Screen

driver_history.png
A driver should be able to view a history of all of their prompts. They should also be able to view quiz history, inspection/tutorial history, and maintenance-action history.

Aside from the Queue prompts, these entries should be in 'story form.' For example:
"On [date], Bekkah took a quiz asking [question1] & [question2]. She answered [answer] and got the answer correct. She gained [##] points, and became a [next level]."

If points are assessed, this should be noted in the story, and if the points result in a 'level up,' this should also be noted.

Queue

The prompt queue, "Queue" window should have a list of all of the prompts that have been put on hold by the user. This view should have the prompt title, and each prompt should be expandable to show details. There should also be a way to re-order the queues and a path to complete the queued prompt from there (exception being the quiz).

Quizzes

The "Quizzes" tab will be a history of all of the quiz prompts the User has completed. There should be an area for data visualizations on top (think Google Analytics), and for each entry, there should be:
  • Date
  • Quiz question(s)
  • User's Answer
  • Correct Answer (if different)
  • The amount of points the user gained towards their next level
  • Each entry should be color coded by the "user's correctness"

Status/Maintenance Stories

This tab will house the results of prompts sent to the User merely for collecting information on the status of the car. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:
  • Date
  • Information requested
  • User's answer
  • Points gained towards next level (if relevant)

Service Stories

This tab will house stories related to users taking action to service their vehicle at a service station, by themselves or by someone else. There should be an area for data visualizations (to be determined later, but think along the lines of Google Analytics), and each entry should include:
  • Date
  • Person who performed service if not Service Station (link to profile if possible)
  • Service Station (link to profile if possible)
  • Technician (if relevant)
  • Location
  • Services performed
  • Car involved (if relevant)
  • Experience rating (review) if relevant
  • If no review was posted, there should be a path for the user to do so from that view.

Research and Results

In our testing, we would like for a majority of our users to find this organization helpful. We also would like to test to ensure that the user can navigate through this screen easily, and complete tasks without a breakdown.

Future Steps

There are many possibilities for this view to evolve to include images in the stories, and to nickname their cars.